Software object property return method and system

ABSTRACT

In one embodiment, a method is provided that includes designating a visual representation of an object in a display screen of a human machine interface, changing the state of the object, and creating an entity in response to the changing, wherein the entity includes any properties, connections and text associated with the object. An interface system is provided that includes a machine readable medium having programming code implementing the method. An industrial automation device is also provided.

BACKGROUND

The present invention relates generally to the field of interfacedevices and to their configuration and programming. More particularly,the present invention relates to techniques for manipulation of objectsof industrial automation devices and their visual representations on theinterface devices.

A wide range of interface devices are known and are presently in use inmany different fields. In industrial automation, for example, humanmachine interfaces or “HMIs” are commonly employed for monitoring orcontrolling various processes. The HMIs may read from or write tospecific registers such that they can reflect the operating state ofvarious machines, sensors, processes, and so forth. The interfaces canalso write to registers and memories such that they can, to some extent,control the functions of the process. In monitoring functions alone,little or no actual control is executed. In many other settings similardevices are employed, such as in automobiles, aircraft, commercialsettings, and a host of other applications. In many applications, theinterface may not communicate with a remote device or process, but maybe operated in a stand-alone manner.

In these interface devices, various objects used in the interface maycorrelate to different controls, monitors, or any other parameter of anindustrial automation device. Some of these objects may have visualrepresentations on the interface devices, while other objects may not bevisually represented but may be accessible for configuration andprogramming by a user. A user may desire to manipulate these objects,such as by creating new objects, deleting objects, or otherwise changingthe state of an object to create and customize an interface.

In some instances, a user may access the interface devices via a clientsuch as a web browser. In either case, the performance andresponsiveness of the interface device or web browser may be affected bymanipulation of the objects of the interface device. For example, thecaching functionality of the web browser may result in caching a largeamount of objects in memory, thus reducing the amount of memoryavailable for execution of the interface. Additionally, transfer of databetween the web browser, the interface device, and the industrialautomation device may also affect the performance and responsiveness ofthe interface device and web browser.

BRIEF DESCRIPTION

The present invention provides a novel approach to interface devicemanagement and configuration designed to respond to such needs. Theapproach uses visual representations of a plurality of device elementsoperative on the interface device. A user may change the state of adevice element, such as deleting the device element, and a user may alsoundo the operation such that the properties, connections, and textassociated with a device element are restored. An entity may be createdin response to the change in state of a device element and transferredto a browser running designer software or other application, so that theentity includes the properties, connections, and text of the originaldevice element.

Methods, devices, and computer programs are all supported for performingthese and other functions of the invention.

DRAWINGS

These and other features, aspects, and advantages of the presentinvention will become better understood when the following detaileddescription is read with reference to the accompanying drawings in whichlike characters represent like parts throughout the drawings, wherein:

FIG. 1 is a general overview of a framework for an interfaceconfiguration system in accordance with certain aspects of the presentinvention;

FIG. 2 is a diagrammatical overview an interface for monitoring orcontrolling a process in accordance with an embodiment of the presentinvention;

FIG. 3 is an overview of certain of the functional components in aninterface and a configuration station in accordance with an embodimentof the present invention;

FIG. 4 is an overview of certain views or containers of device elementsin accordance with an embodiment of the present invention;

FIGS. 5A-5N are an overview of a delete operation and undo operation ondevice elements of an interface in accordance with an embodiment of thepresent invention; and

FIG. 6 is a flowchart illustrating a process for a delete and undooperation on a device element of an interface in accordance with anembodiment of the present invention.

DETAILED DESCRIPTION

A number of facets, components and processes will be described throughthe following discussion. By way of introduction, a general systemoverview is in order that situates these innovations in context. FIG. 1is a diagrammatical representation of a control and monitoring softwareframework 10 for an interface in accordance with an embodiment of thepresent invention. The framework 10 facilitates building functionalsoftware by utilizing a module based interconnection mechanism 12, whichinherently supports dynamic manipulation and configuration. This dynamicmanipulation and configuration ability facilitates efficient provisionof feature-rich configuration environments for configurable interfaces.That is, as described below, individual device elements are provided asstand-alone code that can be individually programmed, pre-written foruse, as in a library, customized in their function and appearance inscreens, and interconnected to provide information to a user as well asmonitoring and control functions.

The framework 10 includes two interrelated software environments thatcan reside on a single system (e.g., computer). Specifically, A run-timeenvironment 14 enables an operator (e.g., a human user) to interact withan application, such as a process during run-time (e.g., during use ofthe interface, typically during interaction with or observance of aprocess in operation). A design-time environment permits a designer toconfigure the interface and its components. For example, a system maygraphically present run-time information to an operator via the run-timeenvironment 14 on a display (e.g., computer or interface device screen).Further, the system may include means (e.g., a keypad) for acceptingoperator input that can be detected and managed via the run-timeenvironment. The environments interact as described in detail below, ininnovative ways to provide greatly enhanced programming and use of theinterface.

The run-time environment includes or provides access to device elements18. The device elements 18 are software components that may include anyaccessible or configurable element in a software environment. Forexample, the device elements 18 include software components, such as“ActiveX” controls or “.NET” components that are managed by the run-timeenvironment 14. “ActiveX” and “.NET” refer to object-oriented concepts,technologies and tools. Those skilled in the art will be well-acquaintedwith such programming approaches generally. In the present context, suchstandards should be taken as merely examples, and “device elements”should be understood as including any generally similar components orself-sufficient programs that can be run as quasi-independent elements,sometimes referred to as “objects”. Other standards and platforms existfor such elements, typically championed by different companies orindustry groups.

Because such device elements are basic to certain of the inventiveconcepts, a few words of introduction are in order. Device elementsgenerally include four features: properties, methods, connections (orconnection points) and communications interfaces. Properties areattributes that can be adjusted, such as to define an image orrepresentation of the element in a screen view, as well as its locationon the screen, and so forth. A method is an executable function(sometimes referred to herein as the elements “functionality” or “stateengine”), and defines an operation performed by execution of theelement. A connection is a link between elements, and can be used tocause data (read from a memory or written to a memory) to be sent toanother element.

Specific examples of device elements 18 may include softwarepushbuttons, timers, gauges, PLC communication servers, screens, andapplications. In general, virtually any identifiable function may beconfigured as such an element. Moreover, as discussed below, suchelements may communicate with one another to perform a wide range ofdisplay, monitoring operations and control functions. It should be notedthat device elements 18 do not require special limitations forsupporting a design mode. Also, while elements associated with an imageare quite useful, particularly for screen views, many elements may nothave a visual representation, but may perform functions within an HMI,such as calculations, or even management and data exchange between otherelements.

The run-time environment typically operates using a communicationssubsystem 20. The communications subsystem 20 is adapted to interconnectthe device elements 18. In practice, the communications subsystem 20 maybe thought of as including the connections of the device elements.However, it may include a range of software, hardware and firmware thatsend data to and receive data from external circuits, such as PLC's,other computers, networks, satellites, sensors, actuators, and so forth.

The run-time environment typically operates using a behavioral subsystem22, which is adapted to manage the behavior of the device elements 18.For example, responsibilities of the behavioral subsystem 22 may includethe following: place and move device elements, modify device elements,group device elements on interchangeable screens, save and restorescreen layouts, manage security, save and restore connection lists, andsupply remote access to the run-time environment 14. Here again, inpractice, such behaviors may be defined as part of the profile (i.e.,the “method” or “state engine”) of each device element.

The design-time environment 16 includes an advanced implementation ofthe behavioral subsystem 22 that facilitates direct or indirectmanipulation of the run-time environment 14, without impeding orcompromising the behavior of the run-time environment 16. That is,design and reconfiguration can be done even while an interface isoperating. The behavioral subsystem 22 extends access to the run-timeenvironment 14 via remote provision of the design-time environment 16,such as in a conventional browser. The behavioral subsystem 22 allows adesigner to interact with and change aspects of the run-time environment14 of an HMI via a remote configuration station by serving thedesign-time environment or aspects thereof to the configuration stationfrom the HMI. For example, an HMI coupled to a laptop via a network mayprovide a user with configuration capabilities by serving up a specificdesign-time environment to the laptop via the network.

Details and examples of how this may be done are provided below. Incurrent embodiments, the design-time environment may be a product ofcombining Dynamic Hypertext Markup Language (DHTML) and an Active ServerPage (ASP) server scripting to serve dynamic content to a browser. AnASP script is specially written code that includes one or more scripts(i.e., small embedded programs) that are processed on a server (e.g.,Web server) before the page is sent to a user. Typically, inconventional usage, such script prompts a server to access data from adatabase and to make a change in the database. Next, the scripttypically builds or customizes the page before sending it to therequestor. As discussed below, such scripting is used in the presentframework quite differently, such as to build screen views without priorknowledge of either the functionality of device elements, or theirinterrelationships.

By facilitating changes to device elements, the design-time environmentallows the designer to make interchangeable design-time models orspecialized implementations of the behavioral subsystem 22. A specificexample of a design-time implementation of the behavioral subsystem 22includes a Web-based design-time environment, which extends access to arun-time environment on an HMI via a TCP/IP connection between the HMIand a remote device. The Web-based design-time environment facilitatesmanagement of the device elements without compromising run-timeperformance or security. In one specialized implementation thebehavioral subsystem 22 gives designers the ability to manipulateaspects of the run-time environment 14 using a Web browser that iscapable of accessing a related interface or HMI. As noted above, and asdescribed in detail below this is achieved by using a combination ofdynamic content, scripting, and configuration of the device elementproperties.

FIG. 2 is a diagrammatical representation of a control and monitoringsystem 24, such as for industrial automation, implementing the frameworkdescribed above in accordance with an embodiment of the presentinvention. The system includes an HMI adapted to interface withnetworked components and configuration equipment. The system 24 isillustrated as including an HMI 26 adapted to collaborate withcomponents of a process 28 through a control/monitoring device 30 (e.g.,a remote computer, programmable logic controller (PLC) or othercontroller). The HMI 26 may physically resemble existing hardware, suchas a panel, monitor or stand-alone device.

Collaboration between the HMI 26 and components of the process 28 may befacilitated by the use of any suitable network strategies. Indeed, anindustry standard network may be employed, such as DeviceNet, to enabledata transfer. Such networks permit the exchange of data in accordancewith a predefined protocol, and may provide power for operation ofnetworked elements. As noted above, while reference is made in thepresent discussion to networked systems and to systems incorporatingcontrollers and other equipment, the HMI 26 and programming techniquesdescribed may be equally well applied to non-networked components (e.g.,GPS displays, game displays, cell phone displays) and to networkedsystems outside the industrial automation field. For example, thearrangements and processes described below may be used in facilitiesmanagement, automotive and vehicular interfaces, computer numericcontrol (CNC) machines, point of sale (POS) systems, control interfacesfor commercial markets (e.g., elevators, entry systems), and so forth,to mention only a few.

The run-time or operation environment constructed and managed by acorresponding behavioral subsystem, is stored on and resident in the HMI26. For example, such a behavioral subsystem can be adapted to load theapplication configuration framework (e.g., 10) from a storage location,such as during initial manufacture or setup of the HMI. When loaded, thestored application framework may be adapted to create screens and locateuser interface device elements (actually images or pictorialrepresentations corresponding to the elements) in the screens. Theseapplications, screens, and user interface elements are each types ofdevice elements. As described below, the HMI 26 includes a storedapplication that dictates the layout and interaction of the deviceelements. The Web-based design-time environment, which is based on arun-time engine, is also loaded and resident on the HMI. The design-timeenvironment may be adapted to handle advanced features (e.g., securitymanagement) for both design-time and run-time environments.

The HMI may be adapted to allow a user to interact with virtually anyprocess. For example, the process may comprise a compressor station, anoil refinery, a batch operation for making food items, a mechanizedassembly line, and so forth. Accordingly, the process 28 may comprise avariety of operational components, such as electric motors, valves,actuators, sensors, or a myriad of manufacturing, processing, materialhandling and other applications. Further, the process 28 may comprisecontrol and monitoring equipment for regulating process variablesthrough automation and/or observation. The illustrated process 28comprises sensors 34 and actuators 36. The sensors 34 may comprise anynumber of devices adapted to provide information regarding processconditions. The actuators 36 may similarly include any number of devicesadapted to perform a mechanical action in response to an input signal.

As illustrated, these sensors 34 and actuators 36 are in communicationwith the control/monitoring device 30 (e.g., a PLC) and may be assigneda particular address in the control/monitoring device 30 that isaccessible by the HMI 26. The sensors 34 and actuators 36 may be indirect communication with the HMI 26. These devices may be utilized tooperate process equipment. Indeed, they may be utilized within processloops that are monitored and controlled by the control/monitoring device30 and/or the HMI 26. Such a process loop may be activated based onprocess inputs (e.g., input from a sensor 34) or direct operator inputreceived through the HMI 26.

The server software on the interface permits viewing of the developmentenvironment, and direct reconfiguration of the interface (particularlyof the device elements and their associated appearance andfunctionality) without the need for special viewing or configurationsoftware. This benefit flows from the fact that the device elements andthe design-time environment itself is resident in the HMI, and “servedup” by the HMI to a browser or other general purpose viewer on theconfiguration station. In other words, necessary support for externalcomputer workstations (e.g., laptop and desktop computers) may bereduced or eliminated. It should be noted that reference to a “browser”for viewing and modifying configuration of the interfaces is not limitedto Web browsers or to any particular browser. References to a browserare intended to be exemplary. More generally, the term “browser” isutilized herein to reference software which includes any general purposeviewer.

The HMI 26, through the programming of the device elements as describedbelow, may be thought of as including instructions for presenting one ormore screen views, and device elements executed upon interaction withthe HMI by reference to the screen views (e.g., pressing a button,touching a location of a screen, and the like). The screen views anddevice elements may be defined by any desired software or softwarepackage. For example, the screen views and device elements may be calledby or executed by an operating system 38. The device elements, asdiscussed above, in accordance with present embodiments, are objectsconforming to “.NET” or “ActiveX” standards. The operating system itselfmay be based upon any suitable platform, such as Window CE. Asreferenced herein, the device elements and tools support Web services ortechnology for transmitting data over networks (e.g., the Internet).These device elements thus follow a set of rules regarding informationsharing and are adapted for use with various scripting and programminglanguages, as described below. Such device elements enable provision ofinteractive content to outside applications such as a LAN, WAN, anintranet, an extranet, or even the World Wide Web. Accordingly, theoperating system 38 and the various device elements facilitate dynamicconfiguration of the HMI 26 through a browser by allowing configurationaccess (e.g., serving up) to the browser.

For example, such configuration access includes access for instantiationof device elements. In other words, new device elements can actually becreated and implemented from the browser. Again, it should be noted thatthe browser does not require actual functional access. Indeed, in oneembodiment, requests via the browser result in a “draw” sequence ofoperations based on data functionality and content of device elements ina container, thus allowing illustration of the device elementrepresentations and access to their configuration without actuallyserving up functional aspects. This allows for configuration via aremote workstation without necessitating technical support for theremote workstation. Such aspects are described in greater detail below.

In addition to the operating system and device elements as describedabove (and as described in greater detail below), the HMI 26 includes anapplication or application layer 40. The application, which may itselfcomprise a device element, facilitates access to and acquisition ofinformation from the various device elements of the HMI. In particular,the application 40 represents a first level in a multi-level deviceelement that can be enumerated for execution. The application 40 in apractical implementation may comprise a user application in the form ofan XML page. The user application is then interacted with by the user oroperator, as well as by the designer as described in greater detailbelow.

The screen views and device elements may be described as independentexecutable pieces of software. In a present implementation, the screenviews are defined by appropriate code written in a markup language(e.g., Hypertext Markup Language or HTML). Thus, the configuration ofgraphical interface screens for the HMI 26 may be performed without theuse of conversion programs. Further, by programming of the deviceelements, the screen views may be developed directly on the HMI 26 viaresident server software (designated as server 42) that makes theresident development environment available for remote access.Specifically, in one embodiment, representations of certain deviceelements (e.g., ActiveX controls) are served up to the browser withoutserving up the software components themselves. Because a development ordesign-time environment may be accessed via a browser, the need todownload changes to the screens and to update remote configurationsoftware applications can be eliminated.

As noted above, device elements may include functionality by which theyread from or write to specific memory or registers of memory, typicallyin other devices (but which could also be within the HMI). For example,a particular function may correspond to writing to or reading from aregister 32 of control/monitoring device 30. In a simple case, forexample, an object simply accesses a piece of data (e.g., a state of acomponent as determined by a sensor), and generates an output signal towrite a value corresponding to the state of a different networkeddevice. Much more complex functionality can, of course, be configured.In an industrial control and monitoring context, for example, suchdevice elements may emulate operation of a range of physical components,such as a momentary contact push button, a push button with delayedoutput, a switch, and so forth. Many pre-programmed device elements maybe available for use by the HMI 26. Such functional modules may beaccessible via a network, or may be resident on the HMI 26, or residenton a separate device directly linked to the HMI 26. In this way, an HMIsupplier or software supplier may provide many possible building blocksfrom which screens and complex control and monitoring functions may beprogrammed. Indeed, a library 44 of available device elements may resideon the HMI 26 to facilitate configuration of the HMI 26, as describedbelow. The screen instructions may call upon the device elements forperforming desired functions based upon operator inputs, and theseinstructions may be programmed into versions of the pre-programmedelements. For example, the operator may provide initiating inputs bytouching a location on a touch screen or depressing keys on a keyboard.Based upon the screen instructions and the device elements associatedwith the instructions (e.g., with specific locations triggering calls orexecution of pre-configured device elements) the desired functions maythen be executed. Accordingly, the operator is enabled to interact witha process, typically to change screen views, write to registers, orcommand the generation of other output or control signals. In astand-alone implementation, the interactions may simply recall or storedata, change screens, and so forth.

One or more separate interface screens may be employed, with some HMIshaving many such screens and a great number of device elements. Eachdevice element may, in turn, be uniquely programmed to consider specificinputs, perform specific functions, and generate signals for specificoutputs. A plurality of such device elements can be loaded and hosted ina single software “container” (e.g., ActiveX container) as describedbelow.

The HMI may be configured by interacting directly with a panel or screenon the HMI itself (if one is present), but in many cases configurationwill be performed from a remote configuration station 46. For example,access is provided directly to the resident library 44 and/or operatingsystem 38 and application 40 via a browser 48 or similar application. Ina present implementation, no other specialized software is required atthe configuration station 46. Indeed, the server 42 resident on the HMI26 may provide access to the device elements in library 44. By storingthe device elements in library 44 directly on the HMI 26, the risk ofversion conflicts and so forth are eliminated or reduced. Additionally,the HMI may be directly connected to the configuration station, oraccessed by reference to an IP address (Internet Protocol address)assigned to the HMI 26.

Access control schemes may be used to limit the ability to changescreens and device elements. For example, a password or user accessstatus may be required to gain such access. Further, in a presentlycontemplated embodiment, the configuration station automaticallyrecognizes the HMI or the terminal on which the HMI is resident as adevice upon being coupled to the configuration station (e.g., similar toan external memory or drive). Thus, once connected to the configurationstation, the HMI may simply be “recognized” as a device that can beaccessed (providing the configuration screen and tools described below).

Once the device elements then resident on the HMI 26 are accessible tothe configuration station 46, aspects of the HMI 26 can be modified orupdated directly on the HMI 26 via the communication link from theconfiguration station 46. For example, a user may wish to update aparticular HMI graphic to provide data, such as historical data ortrending relating to information being received from a newly installedsensor 34. Additionally, the user may find it desirable or convenient toupdate the HMI graphic for presentation of such data while in anoff-line mode (e.g., without immediately implementing the changes). Insuch a scenario, the user may link to the library 44 of available deviceelements via the configuration station 46 and use them to modify the HMIgraphic or functionality in a development environment.

It should be noted that additional device elements can be added to thelibrary 44. For example, if a trending device element is not resident onthe HMI 26, a user can download such an element to the HMI 26 from aconfiguration library 50 resident on the configuration station 46.Alternatively, a user could access the trending device element from aresource library 52 accessible via a network (e.g., the Internet),either directly to HMI 26 or through the configuration station 46. Thismay be particularly beneficial because new and improved device elementscan be downloaded to the HMI 26 individually and on a periodic basis,thus adding new functionality without necessitating the periodic releaseof new conversion programs or HMI operating systems, or run-time ordesign-time environment software. The development environment mayprovide links to such libraries. Further, in embodiments using embeddedcode (e.g., operating system, server software, device objects, etc.),because the embedded code resides on the HMI 26, version conflicts withthe embedded code may be avoided and the necessity for configurationstation software upgrades may be eliminated.

FIG. 3 is a high-level flow diagram representing interaction between anHMI and a configuration station. More detail regarding such processes isprovided below. In general, a platform for the HMI and configurationstation will include the operating system or executive software 38,application software 40, as well as any communication software, amicroprocessor, a network interface, input/output hardware, genericsoftware libraries, database management, user interface software, andthe like (not specifically represented in FIG. 3). In the illustratedembodiment, a design-time platform and a run-time platform interactwithin the HMI. The design-time platform provides views that are servedas the design-time environment 16 to a desktop personal computerplatform (e.g., running a suitable operating system, such as Windows XP,Windows Vista, or Linux) and the run-time platform cooperates with thedesign-time platform via the operating system (e.g., Windows CE, Linux).The design-time platform provides dynamic server content 54, while therun-time platform displays views on the HMI itself (if a display screenis provided on the HMI). The design-time environment 16 is displayed ina browser 48 (e.g., Web browser or other general purpose viewer).

FIG. 3 represents at a very high level how the design-time environment16 interacts with the operating system 38, application 40 and run-timeenvironment 14. The arrow 56 represents dynamic exchange of contentbetween the HMI 26 and configuration station 46. In general, interactionwith the design-time environment is the task of a designer 58 whoinitially configures the HMI screens or views, device elements, theirfunctions and interactions, or who reconfigures such software. Therun-time environment is generally interacted with by an operator 60directly at the HMI. It should be noted that while the design-timeenvironment 16 has specific needs, in a current embodiment, it dependsheavily on the operating system, application and run-time environment.The design-time environment 16 and the run-time environment 14 mayutilize certain base technologies (e.g., DHTML, HTML, HTTP, dynamicserver content, JavaScript, Web browser) to operate respectively in thedesign-time platform and run-time platform. While, in the illustratedembodiment, the run-time environment 14 and the design-time environment26 reside on separate platforms, in some embodiments they may reside onthe same platform. For example, the design-time platform and run-timeplatform may be configured as or considered a single platform.

In one embodiment of the present invention, a design-time Webimplementation is utilized. This design-time Web implementation offersthe speed and flexibility of software running on the design-timeplatform by using a Web browser (e.g., 48) with DHTML support from theHMI, as noted by the dynamic server content 54 in FIG. 3 and asdescribed below. DHTML is used to perform dynamic manipulation of Webcontent in the design-time environment 16. Further, the dynamic servercontent 54 is used in the HMI to serve dynamic Web content to thedesign-time environment 16. This dynamic client-server environmentallows the Web browser to simulate an application running on thedesign-time platform without requiring a piece of software compiled fora related processor.

FIG. 4 is a diagram illustrating one or more device elements in adesign-time environment in accordance with embodiments of the presenttechniques. The diagram includes interactions illustrated byrelationships between a display 100 (e.g., a screen for browserdisplay), a property editor 102, and an HMI 26.

The design-time environment represented by the configuration screen ordisplay 100 includes static content 104 and dynamic content. The dynamiccontent includes images corresponding to any displayed or representeddevice elements 106 (e.g., virtual on/off button, gauge). In oneembodiment of the present techniques, the image is specified by an imagetag in HTML and is part of a JPEG file created by the HMI as describedbelow. The static content 104 may be created by the ASP server or it maypreexist in an HTML file. It should be noted that, in some embodiments,designated designers only can edit the static content 104.

In the representation of FIG. 4, the device element representation 106is contained within a view container 108. As will be appreciated bythose skilled in the art, a container generally defines a portion of aprocessing space in which certain device elements are opened and readyfor use. The container 108 may thus correspond to a first view containerthat includes only the elements viewable within the current screen. Asdiscussed above, many such screens may be provided in the HMI. Otherscreens, such as alternative control or interface screens may beprovided in other view containers, such as a container 110. In general,to speed the operation (e.g., changing between screen views) of the HMI,such view containers are predefined and associated with one another bydefinition of the individual device elements with which they are eitherassociated or within which representations of the device elements areprovided. A global container 112 is defined that include all of thedevice elements necessary for the various view containers, as well asother elements that may not be represented in any view container. Asillustrated in FIG. 4, therefore, view container 108 includes thevirtual button 106 which performs a “jog” function and is manifested bya representation in a first screen. New container 110 includes severalcomponents, such as a “start” button 114, a “stop” button 116, a virtualgage 118 and a digital readout 120. The global container 112, then, willinclude all of these device elements for the various view containers, aswell as any device elements 122 that are required for operation of theviewable device elements but that are not themselves viewable. Suchdevice elements may include elements that perform computations,trending, communications, and a wide range of other functions.

All device elements that are needed for the various views are openedduring operation of the HMI and remain open in a single global container112. However, utilizing aspects of current technologies, known as“tear-offs” any device elements that are not required for viewing oroperation of a current view (i.e., a view currently displayed on the HMIor configuration station view) are reduced in size to reduce the memoryrequirements, processing requirements, and to facilitate operation ofthe HMI. The “torn-off” device elements nevertheless remain open andactive such that change in between screen views is extremely rapid andefficient from memory utilization and processing standpoints.

FIG. 4 also illustrates a property editor 102 in which a user may accessvarious properties of the element 106. As discussed above, the element106 may also include connections and text associated with the element106, which may also be configured by the user via an editor, similar tothe property editor 102.

In an embodiment, the property editor 102 may interact with the HMI 26 aquery string from the browser 48 to a server 96 (e.g., HTTP server) thatis resident on the HMI 26. The server 96 cooperates with an ASP server98 including a dynamic-link library (DLL) 122 to receive and respond toqueries. The DLL 184 allows for storage of executable routines asseparate files, which can be loaded when needed or referenced by aprogram. In the example set forth above, upon receiving the call, thepage is reloaded by the ASP server 98 and the query string is initiallyparsed resulting in evaluation of the move command. Server side scriptsthen access the device element 18 related to the image 106 and to updateits location property. The new property information is then updated onthe page and the page is passed to the browser 48.

FIGS. 5A-5M depict a change in the state of a device element, e.g., thedeletion of a device element, and the corresponding undo operations inaccordance with an embodiment of the present invention. As explainedfurther below, to improve performance and responsiveness of the browser48, in order to save data for later undo operations, modifications tothe state of a device element on the browser 48 result in a capture ofthe state of an device element and a transfer of the state informationto the HMI 26. Additional changes in the state of a device element willresult in additional states being captured and sent to and stored on theHMI 26. In this manner, a user of the browser 48 may manipulate thestate of a device element and rely on previously stored states for undooperations without suffering a decrease in performance of the browser48, HMI 26, or interface and application running in the browser 48.

Beginning with FIG. 5A, a web browser 48 includes a display 100 havingstatic content 104 and dynamic content, as described above. A user mayview and manipulate device element representations 106 and 200 containedwithin a view container 108. The device element representation 106corresponds to the device element 18 on the HMI 26. Additionally, thedevice element representation 200 corresponds to a device element 202 onthe HMI 26.

As mentioned above, the device element representations 106 and 200 maybe any type of device element, e.g., object, such as a control, a gauge,an indicator, etc. Additionally, various non-viewable device elementsmay be included in a global container that may be required for theinterface the user is managing or configuring. In an embodiment, a usermay desire to configure an interface by adding or removing deviceelements in the view container 108, or, alternatively, in a globalcontainer.

In FIG. 5A, to manipulate a device element, a user may first select thedevice element representation 106 as indicated by dashed area 204. Auser may choose to change the state of the device element 18 by theinterface loaded in the browser 48, such as by deleting device elementrepresentation 106. Various other changes to the state of a deviceelement 18 may be performed by a user, such as various levels ofdeletes, changing the properties of a device element 18, changing theconnections of a device element 18, etc. The delete or other statechange command may be sent to the HMI 26, as indicated by arrow 206.

As illustrated, the device element 18 may include various data, such asproperties 208, connections 210 (e.g., connections to other deviceelements), and text 212. The visual representation of the device element106 on the browser 48 is representative of the device element 106 andall of the additional properties 208, connections 210, and text 212,which are stored on the industrial automation device 30. Similarly, thedevice element 202 may include data such as properties 214, 216, and218. As only visual representations 106 and 200 of the device elements18 and 202 is displayed in the browser 48, the data associated with thedevice elements 18 and 202 is not stored on the browser 48, thus freeingup memory or other resources of the browser 48.

As mentioned above, a user can manipulate device element representation106, such as by deleting the representation 106. In an embodiment,deleting the representation 106 may delete the device element 18 fromthe HMI 26. Alternatively, in other embodiments a delete command or avariation thereof may delete the device element representation 106 fromthe view container 108 but retain the device element on the HMI 26.

In the event that a user deletes the device element representation 106,a user may subsequently desire to undo the delete command or otherchange in state of the device element 18. To facilitate storing of thedata necessary for the undo operation, i.e., the state of a deviceelement at the moment a user changes the state, the various properties,connections, and text of the device element may be bundled together andstored as an entity. For example, as illustrated in FIG. 5B and arrow219, as a user executes a delete operation on the device elementrepresentation 106, the HMI 26 “bundles” all of the data of the deviceelement 18 being copied into a separate entity 220. In an embodiment,the entity 220 may be referred to as a “Blob.” The entity 220 mayinclude data to capture the state of the device element 18, suchproperties 222, connections 224, and text 226 that correspond to theproperties 208, connections 210, and text 212 of the device element 18being deleted. Although the data of a device element may be stored inthe entity 220, the entity 220 is not usable as the device elementitself, but instead is used for storing, serializing, and transferring adevice element and all of its associated properties, connections, andtext. Additionally, as mentioned above, creating the entity 220 on theHMI 26 where the device element 18 is stored ensures that the undooperation will include all of the data associated with the deviceelement 18.

As illustrated in FIG. 5C, after the entity 220, the entity 220 may beserialized and transferred to the web browser 48, as indicated by arrow228, such as via HTTP or any suitable protocol. In one embodiment, theentity 220 may formatted in Extensible Markup Language (XML) format. Inother embodiments, the entity 220 may be described in any suitableformat. Further, in some embodiments, the entity 220 may be compressedbefore serialization and transfer, to minimize the size of the entity220 and increase the speed of the transfer. Additionally, in alternateembodiments, the entity 220 may be stored in a non-volatile memory ofthe HMI 26, such as saved to a hard disk drive, flash memory, etc.

As illustrated in FIG. 5D, the entity 220 may now be stored in theapplication running the web browser 48 after completion of the deleteoperation. The delete operation is completed on both the browser 48 andthe HMI 26. For example, the device element 18 may be removed from theHMI 26, such that only device element 202 is left on the HMI 26.Similarly, the device element representation 106 is deleted from thebrowser 48, leaving only device element representation 200.

To insure future undo operations, the web browser 48 and any applicationexecuting therein only stores the entity 220. Because the entity 220 issmaller than the device element 106, such as through data aggregationand compression as discussed above, the entity 220 uses significantlyless resources of the web browser 48 and associated computer.Additionally, the web browser is only storing entities for undooperations, such as for the state of those device elements that havebeen changed, so not all device elements or entities thereof need to bestored.

FIGS. 5E though 5H illustrate deletion of another device element 202 andstacking of “blobs” for subsequent undo operations. As shown in FIG. 5E,a user may select another device element representation 200, as shown bydashed area 230, to change the state of device element 202, such as bydeleting. As previously stated, because of the previous delete operationon device element 18, an entity 220 is stored on the browser 48 thatincludes the state of device element 18 at the moment of deletion.

Similar to the deletion of device element 18, once a user selects deviceelement representation 200 and initiates a delete operation, the deleteoperation is communicated to the HMI 26 (arrow 232) and an entity 234,or “blob,” is created on the HMI 26 to capture the state of deviceelement 202, as in FIG. 5F. The entity 234 may include the properties214, connections 216, and text 218 of device element 202. As statedabove, the entity 234 is used for storing, serializing, and transferringthe data that includes the state of device element 202 at the time ofdeletion.

As illustrated in FIG. 5G, the second entity 234 may be transferred tothe browser 48 (arrow 236) to store for any subsequent undo operations.Both the previously created entity 220 and the second entity 234 arestored in the browser 48. The entities 220 and 234 and any subsequentlycreated entities may be stored according to a last-in-first-out (LIFO)principle, so that the next undo operation will case the last receivedentity to be transferred back to the HMI 26. In FIG. 5H, aftercompletion of the delete operation, the device representation 200 isdeleted from the browser 48 and, correspondingly, the device element 202is deleted from the HMI 26.

FIGS. 5I-5N illustrate an undo operation that restores a device elementfrom a stored entity in accordance with an embodiment of the presentinvention. As shown in FIG. 5I, a user may desire to undo the deletionof device element 202 by selecting the appropriate undo command from theinterface of the application in the browser 48. As illustrated by thedashed area 236, after a user initiates the undo operation the deviceelement representation 200 may appear in the browser 48, and the undooperation is communicated to the HMI 26 (arrow 238). As stated above,the undo operation may cause the last received entity to be transferredto the HMI 26. For example, as shown in FIG. 5J, for the undo operationof the deletion of the device element 202, the entity 234 may betransferred back to the HMI 26 as illustrated by arrow 238. Thepreviously received entity 220 remains stored on the browser 48.

As shown in FIG. 5K, once the HMI 26 receives the entity 234, the HMI 26deserializes and unpacks the entity 234, restoring the device element202 on the HMI 26. Additionally, in some embodiments the entity 234 maybe compressed before sending to the HMI 26, thus the HMI 26 may alsodecompress the entity 234. Because the entity 234 stored the connections214, properties 216, and text 218 of the device element 202 at the timeof the change in state of the device element 202, e.g., the deleteoperation, the restoring the device element 202 from the entity 234restores the device element 202 to its state just prior to the deleteoperation. In this manner any change in state may be preserved forsubsequent undo operations.

A user may also desire to undo the change in state, e.g., deletion, ofother device elements, such as device element 18. As shown in FIG. 5L, auser may initiate an undo operation of the deletion of device element18, as shown by the appearance of device element representation 106 anddashed area 240. Again, the undo operation may be communicated to theHMI 26, as shown by arrow 242. During the undo operation, the entity 220is transferred to the HMI 26, as illustrated in FIG. 5M by arrow 242.Again, in one embodiment the entities may be stored and accessedaccording to a last-in-first out, so that an undo of the previousoperation causes the next-oldest entity to be transferred t the HMI 26.As stated above, once the HMI 26 receives the entity 220, itdeserializes and unpacks the entity 220, and may also decompress theentity 200 if the entity has been compressed before transfer. Becausethe entity 200 was created just prior to the change in state, e.g.,deletion, of the device element 18, upon restoration of the deviceelement 18 from the entity 234, all the properties 208, connections 210and text 212 associated with device element 18 are restored, as shown inFIG. 5N. Thus, as a result of two consecutive undo operations, thedevice elements 18 and 202 are restored to the HMI 26, as depicted bythe device element representations 106 and 200.

FIG. 6 illustrates a process 300 illustrating the undo operationexecution as described in FIGS. 5A-5L in accordance with an embodimentof the present invention. Initially, a user may select a visualrepresentation of a device element in a screen of a web browser (block302) running in an application, e.g. a design application forconfiguring an industrial automation device. A user may then select adelete operation on the selected device element (block 304). Theinitiation of the delete operation is communicated to the HMI (block306), which then creates an entity that includes all of the properties,connections, and text included with the design element (block 308).

Once the entity for a design element is created, the entity may becompressed to reduce the size of the entity (block 310). Aftercompression, the entity is serialized and transferred to the web browserand design application (block 312), via HTTP or any other suitableprotocol. The HMI 26 may delete the device element from the HMI, and thecorresponding device element representation may be removed from thebrowser 48 (block 314). A user may then select an undo operation on theselected device element (block 316). The initiation of the deleteoperation initiates transfer of the entity to the HMI (block 318). Theindustrial automation device deserializes and unpacks the entity,creating a copy of the original device element (block 320). Thus, at theend of the operation, the device element (block 322) is restored on theHMI in the same state as before the deletion.

While only certain features of the invention have been illustrated anddescribed herein, many modifications and changes will occur to thoseskilled in the art. It is, therefore, to be understood that the appendedclaims are intended to cover all such modifications and changes as fallwithin the true spirit of the invention.

1. A method, comprising: designating a visual representation of anobject in a display screen of a human machine interface; changing thestate of the object; and creating an entity in response to the changing,wherein the entity includes any properties, connections and textassociated with the object.
 2. The method of claim 1, wherein changingthe state of a object comprises changing any properties, connections,text, and/or combination thereof of the object.
 3. The method of claim1, wherein changing the state of object comprises deleting the object.4. The method of claim 1, comprising sending the entity from anindustrial automation device to the human machine interface.
 5. Themethod of claim 1, comprising storing the entity on the human machineinterface.
 6. The method of claim 1, comprising sending the entity fromthe human machine interface to an industrial automation device.
 7. Themethod of claim 1, comprising accessing the entity and restoring theproperties, connections, and text of the object on the industrialautomation device.
 8. The method of claim 1, comprising compressing theentity.
 9. The method of claim 1, wherein the entity is described via amarkup language.
 10. The method of claim 4, wherein sending the entitycomprises sending the entity from an industrial automation device to thehuman machine interface via a hypertext transfer protocol.
 11. Themethod of claim 5, wherein sending the entity comprises sending theentity from the human machine interface to the industrial automationdevice via a hypertext transfer protocol.
 12. An interface system,comprising a machine readable medium, and programming code stored on themachine readable medium comprising instructions for: designating avisual representation of an object in a display screen of a humanmachine interface; changing the state of the object; and creating anentity in response to the changing, wherein the entity includes anyproperties, connections and text associated with the object.
 13. Themethod of claim 12, wherein changing the state of a object compriseschanging any properties, connections, text, and/or combination thereofof the object.
 14. The method of claim 12, wherein changing the state ofobject comprises deleting the object.
 15. The method of claim 12,wherein the programming code stored on the machine readable mediumcomprises instructions for sending the entity from an industrialautomation device to the human machine interface.
 16. The method ofclaim 12, wherein the programming code stored on the machine readablemedium comprises instructions for sending the entity from the humanmachine interface to an industrial automation device.
 17. The method ofclaim 12, comprising storing the entity on the human machine interface.18. The method of claim 12, wherein the programming code stored on themachine readable medium comprises instructions accessing the entity andrestoring the properties, connections, and text of the object.
 19. Anindustrial automation device having a visual component, comprising: auser viewable screen displaying a visual representation of an object,wherein the object comprises a plurality of properties, connections, andtext associated with the object; and a memory configured to storeprogramming code comprising instructions for: creating an entity inresponse to a change in state of the object, wherein the entity includesany properties, connections and text associated with the object.
 20. Thedevice of claim 19, wherein the user viewable screen comprises a dynamicHTML page.
 21. The device of claim 19, wherein the user viewable screencomprises a web browser.
 22. The device of claim 19, wherein a change instate of a object comprises a change in any properties, connections,text, and/or combination thereof of the object.
 23. The device of claim19, where in a change in state of a object comprises a deletion of theobject.
 24. The device of claim 19, wherein the a user viewable screenis connected to a human machine interface.